-- card: 8511 from stack: in.6
-- bmap block id: 0
-- flags: 0000
-- background id: 3411
-- name: Type 5 XCMD


-- part 5 (button)
-- low flags: 80
-- high flags: A003
-- rect: left=295 top=151 right=173 bottom=395
-- title width / last selected line: 0
-- icon id / first selected line: 0 / 0
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: Type 5 Help
----- HyperTalk script -----
on mouseUp
  ShowDialog 5,4746,3
end mouseUp



-- part 4 (button)
-- low flags: 00
-- high flags: 0000
-- rect: left=11 top=4 right=64 bottom=78
-- title width / last selected line: 0
-- icon id / first selected line: 529 / 529
-- text alignment: 1
-- font id: 0
-- text size: 12
-- style flags: 0
-- line height: 16
-- part name: SD


-- part contents for background part 21
----- text -----
ShowDialog XCMD Type 5

-- part contents for background part 30
----- text -----
17

-- part contents for background part 18
----- text -----
Due to the complexity of many sophisticated stacks, providing some sort of interactive help to the end user is a must.  One of the best methods is to create a button or handler that displays a field containing some kind of information.  This is acceptable when your help consists solely of text.  But when your help screens require both text AND graphics your only alternatives are to display a (normally hidden) card picture, go to a "help" card, or to go to a card on a companion "help" stack.

Each method has a drawback.  Showing a normally hidden card picture is fine so long as you don't ALREADY have a card picture.  The disadvantage of having help cards in your stack is that you have to figure out some way to "lock out" the help cards so that the end user won't "stumble" onto them while casually browsing the stack.  Having a secondary Help stack circumvents this problem, but then you have to worry about the Help stack being available (You risk getting a "Where is..." dialog box if the Help stack is missing, renamed, or in another folder).

ShowDialog Types 5 & 6 provide a method for the display of interactive help screens containing BOTH text AND (color) graphics, that are contained in the stack, but are out-of-sight until needed.

ShowDialog XCMD Type 5 displays a dialog containing buttons that, when clicked, will display a corresponding PICT within the dialog.  The buttons 
"gray out" to indicate which one is currently selected.  Clicking on the Cancel button, or hitting enter or return dismisses the dialog.  The PICTs can contain any amount of text and graphics, and can be in color if you wish.



-- part contents for background part 15
----- text -----
ShowDialog Type 5 parameters are:

ShowDialog 5,<DLOG resource ID>,<button # grayed out>,[<top coord>,<left coord>]

where 5 is the type of the external;
<DLOG resource ID> is the resource ID of the DLOG template;
<button # grayed out> is the DITL item # of the button that will be initially grayed out when the dialog is first displayed.  Its corresponding PICT will be displayed. 

Once again, the last two parameters, for specifying the location of the dialog, are OPTIONAL.

A PICT is made to correspond to a particular button by adding 1000 to the DITL item # of the button.
Thus, button #3 will show PICT ID 1003, button #4 will show PICT ID 1004, and so on.



-- part contents for background part 17
----- text -----
Follow this outline when constructing the DITL resource:
DITL item# 1: an ENABLED button.  This will be the Cancel button.  
DITL item# 2: a DISABLED useritem.  This item will be the area into which the PICTs will be drawn and, consequently, should be made large.

The remaining items should be ENABLED buttons.  Give the buttons descriptive names so the user will know why to click a particular button.  

The dialog is dismissed by clicking Cancel or hitting enter or return.
If a required PICT resource is missing, the dialog will beep and appear with a blank display.

Notice how the buttons gray out when you select them.